feat: confidential container for zero trust validated pattenr docs #628
Conversation
Signed-off-by: Chris Butler <chris.butler@redhat.com>
gaurav-nelson
force-pushed
the
coco-ztvp
branch
from
e59406f to
b206e80
Compare
|
@butler54: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
|
||
| * link:https://docs.redhat.com/es/documentation/red_hat_trusted_profile_analyzer/2.2[Red{nbsp}Hat Trusted Profile Analyzer (RHTPA)] | ||
| ** Provides the storage and management means for _Software Bill of Materials_ (SBOMs), with cross-referencing capabilities between SBOMs and CVEs/Security Advisories. | ||
| Optionally: |
There was a problem hiding this comment.
| Optionally: | |
| Optionally: |
| Red{nbsp}Hat's link:https://docs.redhat.com/en/documentation/openshift_sandboxed_containers/1.11/html/deploying_confidential_containers/index[OpenShift sandboxed containers Confidential Containers] (CoCo) feature uses Trusted Execution Environments (TEEs). TEEs are specialized CPU features from AMD, Intel, and others that create isolated, encrypted memory spaces (data in use) with cryptographic proof of integrity. | ||
| These hardware guarantees mean workloads can prove they have not been tampered with, and secrets are protected, even from infrastructure administrators. | ||
|
|
||
| Confidential containers within the layered zero-trust pattern integrate zero-trust workload identity management. |
There was a problem hiding this comment.
For zero-trust workload identity management, are we referring to the concept or the product?
|
@sabre1041: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
2 participants
Signed-off-by: Chris Butler chris.butler@redhat.com